Performance Charts must be configured with memory leak protection.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-256625	VCPF-70-000015	SV-256625r888366_rule		Medium

Description
The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, Performance Chart can continue to consume system resources, which will lead to "OutOfMemoryErrors" when reloading web applications. Memory leaks occur when JRE code uses the context class loader to load a singleton. This will cause a memory leak if a web application class loader happens to be the context class loader at the time. The "JreMemoryLeakPreventionListener" class is designed to initialize these singletons when Tomcat's common class loader is the context class loader. Proper use of JRE memory leak protection will ensure the hosted application does not consume system resources and cause an unstable environment.

Description

The Java Runtime environment can cause a memory leak or lock files under certain conditions. Without memory leak protection, Performance Chart can continue to consume system resources, which will lead to "OutOfMemoryErrors" when reloading web applications. Memory leaks occur when JRE code uses the context class loader to load a singleton. This will cause a memory leak if a web application class loader happens to be the context class loader at the time. The "JreMemoryLeakPreventionListener" class is designed to initialize these singletons when Tomcat's common class loader is the context class loader. Proper use of JRE memory leak protection will ensure the hosted application does not consume system resources and cause an unstable environment.

STIG	Date
VMware vSphere 7.0 vCenter Appliance Perfcharts Security Technical Implementation Guide	2023-02-21

Details

Check Text ( C-60300r888364_chk )
At the command prompt, run the following command: # grep JreMemoryLeakPreventionListener /usr/lib/vmware-perfcharts/tc-instance/conf/server.xml Expected result: If the output of the command does not match the expected result, this is a finding.

Fix Text (F-60243r888365_fix)
Navigate to and open: /usr/lib/vmware-perfcharts/tc-instance/conf/server.xml Navigate to the node. Add '' to the node. Restart the service with the following command: # vmon-cli --restart perfcharts